Providing Advanced Playback And Control Functionality To Video Client

ABSTRACT

Systems and methods for providing playback features to a device are disclosed. A manifest may be generated, which may comprise data associated with a content asset. A state file may be generated, which may comprise data associated with the manifest. Using one or more of the manifest and the state file, a device may modify segments of the content asset or may playback segments of the content asset.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.14/976,535, filed on Dec. 21, 2015.

BACKGROUND

Many devices are capable of connecting to a network such as the Internetto stream video. More robust devices are capable of not only connectingto and streaming video, but also of decoding tags in the video streamitself. Such tags can be decoded to provide additional functionalitylike advertising cues, advanced playback controls, and restriction andentitlement logic. However, a growing number of simple devices (e.g.,browsers implementing HTMLS) do not have the necessary capability todecode the embedded tags and therefore, are not able to access theadditional functionality provided by such tags. These and othershortcomings are identified and addressed by the disclosure.

SUMMARY

Methods and systems for providing advance playback and controlfunctionality to a video client are disclosed. The methods and systemsdisclosed may allow user devices (e.g., content playback devices, mediaplayers, etc.) to determine time-related information associated withmanifests being processed by the user devices. As an example, a statefile may be generated and provided to the user devices to facilitatedetermination of such time-related information. The state file maycomprise information such as a time code and/or an event markerassociated with the generation of a manifest. As such, the user devicemay receive the manifest and a synchronized state file and may processthe state file to facilitate the execution of advanced playback andcontrol functionality (e.g., advertising cues, advanced playbackcontrols, and restriction and entitlement logic).

The methods and systems may comprise generating a manifest associatedwith at least a first segment of a content asset. The manifest maycomprise a first time code. A state file may also be generatedcomprising a second time code to allow synchronization with the firsttime code of the manifest. The manifest and the state file may betransmitted to a recipient device, wherein processing of the state filefacilitates one or more playback features associated with at least thefirst segment of the content asset.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an example network;

FIG. 2 is a representation of an example interface;

FIG. 3 is a representation of an example system and data flow;

FIG. 4 is a flow chart of an example method;

FIG. 5 is a flow chart of an example method;

FIG. 6 is a flow chart of an example method; and

FIG. 7 is a block diagram of an example computing system.

DETAILED DESCRIPTION

Various devices (e.g., media players) may not configured to decodecertain embedded information from a content stream such as an IP videostream. The systems and methods of the present disclosure provide amechanism to allow such devices to obtain information associated with acontent stream that was previously not available to the devices. As anexample, a manifest can be generated associated with a particularcontent asset. Along with the manifest, a supplemental file, such as astate file can be generated and provided to the user devices along withthe manifest. The state file can include information such as a timecode, an event marker, and/or additional metadata associated with theplayback and control features of the user device. The information in thestate file can be processed by the receiving user device to facilitatethe execution of advanced playback and control functionality (e.g.,advertising cues, advanced playback controls, and restriction andentitlement logic). The state file can be generated as part of thetranscoding process of the underlying content stream and can besynchronized in time with the associated manifest, for example, usingthe embedded time code as a synchronization marker. These and otheraspects will be discussed in reference to the accompanying figures.

FIG. 1 illustrates various aspects of an exemplary network in which thepresent methods and systems can operate. Those skilled in the art willappreciate that present methods may be used in systems that employ bothdigital and analog equipment. One skilled in the art will appreciatethat provided herein is a functional description and that the respectivefunctions can be performed by software, hardware, or a combination ofsoftware and hardware.

A system 100 and network can comprise a user device 102 in communicationwith a computing device 104, such as a server, for example. Thecomputing device 104 can be disposed locally or remotely relative to theuser device 102. As an example, the user device 102 and the computingdevice 104 can be in communication via a network 105 such as private orpublic network (e.g., Internet). Other forms of communications can beused, such as wired and wireless telecommunication channels, forexample.

In an aspect, the user device 102 can be an electronic device such as acomputer, a smartphone, a laptop, a tablet, a set top box, or otherdevice capable of communicating with the computing device 104. As anexample, the user device 102 can comprise a web browser 106 forproviding an interface to a user to interact with the user device 102and/or the computing device 104. The web browser 106 can be anyinterface for presenting information to the user and receiving a userfeedback such as Internet Explorer, Mozilla Firefox, Google Chrome,Safari, or the like. Other software, hardware, and/or interfaces can beused to provide communication between the user and one or more of theuser device 102 and the computing device 104. As an example, the webbrowser 106 can request or query various files from a local sourceand/or a remote source.

In an aspect, the user device 102 can comprise an interface 108 such asa user interface or API. As an example, the interface 108 can beconfigured to provide a visual presentation, audio presentation,interactive communication, and the like. As a further example, interface108 can comprise one or more interface elements 110. In an aspect, theinterface elements 110 can comprise a menu, icon, user-selectablebutton, drop-down, slider bar, input field, and the like. As an example,one or more of the interface elements 110 can be configured to receive aselection or input from a user.

The user device 102 can comprise a media player 112 configured toprocess information to cause playback of content via the interface 108.In an aspect, the media player 112 may comprise the web browser 106and/or software to effect playback of content and features relating tosuch playback. As an example, the media player 112 can be configured totransmit a request, such as a HTTP GET or POST request over network 105to the computing device 104. The user device 102 can also explicitlysend parameter data to the computing device 104 voluntarily or inresponse to a request for client parameters. The computing device 104may then evaluate various business rules and may retrieve or generate amanifest 118 (or manifests), which can then be passed back to userdevice 102 over network 105 and placed into storage 114.

The media player 112 can process the manifest 118 to playback videocontent via the interface 108. For example, the manifest 118 mayreference one or more segments of a content asset 119, for example, instorage: 124. Thus, the manifest 118 may comprise a playlist file suchas a M3U8 playlist file. The media player 112 may then request, stream,decode, and output the referenced content segments seamlessly to theinterface 108 to playback the requested portion of the content asset119. Although reference is made to the manifest 118, it is understoodthat any number of manifests may be used in a similar manner.

As an example, the storage device 124 can be in communication with oneor more of the user device 102 and the computing device 104 tosend/receive data such as content segments and/or index informationassociated with one or more content asset 119. As a further example, thestorage device 124 can be located remotely from the user device 102,such as a network storage medium, network digital video recorder system,and the like. In an aspect, to manage the content asset 119 (or assets)accessed via the storage device 124, and/or other devices, a manifest(e.g., manifest can be generated as an index of data stored in one ormore locations and/or in one or more storage mediums.

In an aspect, one or more software components such as plug-ins 116 canbe provided to the user device 102. As an example, plug-ins 116 cancomprise an extension or software component that adds specific abilitiesto another software application. As an example, one or more plug-ins 116can be configured to customize the functionality of a particularapplication such as the interface 108.

In an aspect, the computing device 104 can be a network device such as aserver (e.g., manifest server) for communicating with the user device102. As an example, the computing device 104 can communicate with theuser device 102 for providing services such as network (e.g., IP)services using one or more protocols (e.g., FTP, HTTP, etc.).

In an aspect, the computing device 104 can manage the communicationbetween the user device 102 and storage 120 for sending and receivingdata therebetween. As an example, the storage 120 can store a pluralityof data sets, manifest 118, content asset 119, user identifiers orrecords, authentication information, or other information. As a furtherexample, the user device 102 can request and/or retrieve a file from thestorage 120 such as the manifest 118. The storage 120 can be integratedwith the computing device 104 or some other device or system.

In an aspect, the computing device 104 can be configured toencode/transcode the content asset 119 such as a content stream receivedfrom a content source 121. Although reference is made to the contentasset 119, it is understood that any number of content assets may beused in a similar manner. The content asset 119 can be or compriselinear (e.g., live) broadcast content and/or non-linear (e.g., video ondemand, recorded, etc.) content. As an example, the computing device 104can receive a linear content stream (e.g., content asset 119) in a firstformat such as MPEG-2 and can transcode the content stream into a secondformat such as MPEG-4. The computing device 104 can be configured toprovide a plurality of content segments (e.g., 2 second playbacksegments) representing the content stream and can store the contentsegments for subsequent retrieval. The computing device 104 can generatea manifest (e.g., manifest 118) including information relating to theretrieval of the content segments for playback. The computing device 104can generate a state file 122 associated with the content segmentsand/or the manifest. For example, the state file 122 can compriseinformation such as a time code 126 associated with the transcoding timeof the content segments and/or the generation of the associatedmanifest. The state file 122 can comprise an event marker 128 associatedwith the content segments and/or the manifest 118. As an example, theevent marker 128 can represent a version of the manifest 118.

In another aspect, the manifest 118 can comprise the locations ofvarious quality level (bitrate and resolution) content segments locatedat network storage or local device storage or combination thereof. As anexample, a device can receive the manifest 118 and can dynamicallyrequest particular data to be received. Transmission of any combinationvarious content segments having varying network/local storage locationscan be facilitated on the segment-by-segment basis using a plurality ofmanifests (e.g., manifest 118). For example, a plurality of themanifests 118 can be updated on a segment-by-segment basis by thecomputing device 104.). One or more of the manifests 118 can represent aversion of another one of the manifest 118. For example, one manifest118 may represent a particular bit rate of a content segment, whileanother version of the manifest 118 represents the same content segmenthaving a different bit rate. Such versions of the manifests 118 caninclude differences such as language (e.g., audio and/or closedcaptioning options), image dimensions, output limitations such asaudio-only, and the like.

The manifests 118 can provide location information that can be processedby the user device 102 (e.g., the media player 112 executing via theuser device 102) to facilitate locating and/or requesting particulardata segments (e.g., content segments) from one or more of a pluralityof sources. As such, the user device 102 or other recipient device ofthe manifest(s) 118 can use the manifest to retrieve content forpresentation to a user, for example via an interface such as interface108, shown in FIG. 2.

By way of example, the interface 108 (FIG. 2) can be loaded to the userdevice 102 as an add-on software package. The methods and systemsdisclosed can utilize one or more interfaces 108 to perform one or morefunctions in one or more locations. FIG. 2 illustrates an exemplaryinterface 108 for performing the disclosed methods. This exemplaryinterface 108 is only an example of an interface and is not intended tosuggest any limitation as to the scope of use or functionality ofinterface architecture. Neither should the interface 108 be interpretedas having any dependency or requirement associated with any one orcombination of components illustrated in the interface 108.

In an aspect, the interface 108 can comprise a viewing window 202 fordisplaying information (e.g. web pages, files, etc.) to the user. As anexample, the interface 108 can comprise an address bar 204 or URL bar toallow a user to input a URL for directing the requests of the interface108. In an aspect, the interface 108 can comprise a toolbar disposedadjacent the address bar 204 of the interface 108 and including one ormore interface elements, buttons, or engageable menus. The interface 108can be presented to the user in any position, form, and environment. Asan example, the interface 108 can comprise a plurality of interfaceelements, such as user-engageable buttons 206 for executing variousassociated functions (e.g. search function, settings modification, play,pause, seek, and the like.)

In an aspect, the interface 108 can comprise an interface element suchas home button, preset function, or pointer for directing the interface108 to a pre-defined file or webpage, and/ or a plug-in, extension, oran application 208 requiring a plug-in or extension. In another aspect,the interface 108 can be configured to present data to a user such asvia the viewing window 202. As an example, the interface 108 can presentcontent 210 to a user. As a further example, the interface elements canbe used to interact with the content 210.

FIG. 3 is a block diagram of an example system according to aspects ofthe present disclosure. In an aspect, a device such as the user device102 and/or the media player 112 can be configured to receive one or more(e.g., a series) of manifests such as the manifest 118. The manifest 118(or manifests) can comprise identifiers associated with one or morecontent assets such as videos, segments, data blocks, and the like. Inan aspect, the manifest 118 can comprise information associated with oneor more segments of the content assets such as location, bitrate,resolution, and the like. When the location of one or more of the datasegments is changed, one or more of the manifests 118 can be modified toreflect the updated location of the data segments. As an example, adevice, such as computing device 104 (FIG. 1), can be configured tomonitor locations of one or more data segments or items and canautomatically update the manifest 118 to reflect up-to-date locationinformation of the data segments. As a further example, informationassociated with the location of the data segments can be accessed orreceived and the manifest 118 can be generated in real-time.

In one aspect, the manifests 118 can comprise an index of data segmentssuch as segments of a content asset. The index can comprise an indexvalue associated with each data segment. The index values can indicatetemporal order for playback of the data segments. For example, the indexvalues can be time values according to a time length of playback of thecontent. The time values can be based on a time scale associated withthe content asset. As a further example, the time scale can begin atbeginning of the content and end at the end of the content. In anotheraspect, the index value can comprise a number indicating the place ofthe data fragment in the sequential order of playback.

In one aspect, the manifests 118 can comprise location identifiersconfigured to indicate the location where the data segments can beaccessed. For example, the location of each data fragment can beindicated by a uniform resource identifier, such as a uniform resourcelocator (URL). The URL can comprise, for example, a hypertext transferprotocol link or other link.

In one aspect, a device such as the user device 102 and/or the mediaplayer 112 can be configured to receive one or more of the state files122. The state files 122 can comprise information such as a time codeassociated with the transcoding time of the content segments and/or thegeneration of the associated manifest. One or more of the state files122 can comprise an event marker associated with the content segmentsand/or the manifest 118. As an example, the event marker can represent aversion of the manifest 118. One or more of the state files 122 cancomprise supplemental information associated with the execution of aplayback features such as permissions, advertisement insertion, trickplay features, and the like.

As an example, one or more of the state files 122 can compriseinformation associated with access restrictions associated with the datafragments. For example, one or more of the state files 122 can compriseinstructions that specific data segments are not to be skipped inplayback of the content. In another aspect, one or more of the statefiles 122 can comprise indications of media format (e.g., MIME typessuch as video/mp4), type of delivery (e.g., live streaming format withaccess patterns that accommodate potentially infinite duration, oron-demand format where the content duration is known and finite),digital rights management (DRM) information used for playback,indications for multilingual content (e.g., audio and data fragmentsassociated with specific languages), and the like. One or more of thestate files 122 may include information associated with contentmanipulation such as trick play features, bugs, overlays, or othergraphical controls that can be customized to the version of anassociated manifest 118.

In an aspect, the media player 112 can receive the manifests 118 and canrequest particular data segments to be received based at least on thereceived manifest 118. Transmission of any combination of various datasegments having varying quality level and network/local storage locationcan be facilitated on a segment by segment basis based on the manifest118. As an example, a first one of the manifest 118 can relate to afirst content segment 300 of a non-linear content asset (e.g., contentasset 119), wherein the first content segment 300 has a playbackduration that is less than the playback duration of the entirenon-linear content asset.

The computing device 104 and/or the media player 112 can process atleast one of the state files 122 to determine which version of themanifest 118 is being used to retrieve content and/or which version ofthe manifest 118 is intended to be provided to a particular user device102. As such, computing device 104 and/or the media player 112, plugins,and/or software applications interfacing with the media player 112 canknow what content is being processed by the media player 112 based onthe version of the manifest 118 parsed from the state file 122. Sincethe version of the manifest 118 is known and the content is known,various playback features can be executed that relate to the specificcontent in playback. Accordingly, the media player 112 that may not beable to parse certain embedded information from a content stream, mayinstead process the distinct state file 122 to facilitate playbackfeatures that were previously unavailable.

When the media player 112 reaches the end of the first one of themanifests 118, the user device can request and receive a second one ofthe manifests 118 to continue the seamless playback of content such asthe next segment of the non-linear content asset or an advertisement,etc. As new manifests 118 are generated and transmitted to the mediaplayer 112, new state files 122 can be generated and transmitted in timesynchronization with associated manifests 118.

FIG. 4 illustrates an example method for managing playback of content.In step 402, a request for a manifest can be received or accessed by acomputing device (e.g., the computing device 104) such as a manifestserver, for example. The manifest can comprise information associatedwith a location of one or more segments of a content asset such as an IPaddress, identifier of one or more content assets (e.g., advertisements,video on demand assets, recorded asset) browser or operating platform,device identifiers, browser cookies or login details, screen resolutionof display, and other device, display, content, or user parameters. Asan example, a user device and/or a media player executing on the userdevice can comprise a web browser (e.g., HLS enabled web browser). Theuser device can display a list of available content. For example, a usercan use the media player to navigate to a website presenting a list ofavailable content. After the user selects the content for playback, arequest for the first manifest, such as a HTTP GET or POST request, canbe sent over a network to the computing device. For example, the userdevice can receive a selection of an available content and can transmita request for the first manifest.

In step 404, a manifest can be generated. In an aspect, the manifest canbe generated in response to the request for the manifest. However, amanifest can be generated in response to encoding/transcoding of contentand can be stored for subsequent retrieval. The manifest can compriseinformation associated with a location of one or more segments of acontent asset. As an example, the computing device 104 (FIG. 1) cangenerate (e.g., create, retrieve, cause to be transferred, etc.) amanifest (or manifests), which can then be transmitted to the userdevice 102 over a network.

In step 406, a state file can be generated. As an example, the computingdevice 104 (FIG. 1) can generate (e.g., create, retrieve, cause to betransferred, etc.) the state file (or state files), which can betransmitted to the user device 102 over a network. The state file canrelate to the content segments and/or the manifest. For example, thestate file can comprise information such as a time code associated withthe transcoding time of the content segments and/or the generation ofthe associated manifest. The state file can comprise an event markerassociated with the content segments and/or the manifest. As an example,the event marker can represent a version of the manifest. As such, theevent marker can be used to validate which manifest is being processedto retrieve content and customized playback features can be madeavailable based on the particular version of the manifest.

As an example, the state file can comprise information associated withaccess restrictions associated with the data fragments. For example,state file can comprise instructions that specific data segments are notto be skipped in playback of the content. In another aspect, the statefile can comprise indications of media format (e.g., MIME types such asvideo/mp4), type of delivery (e.g., live streaming format with accesspatterns that accommodate potentially infinite duration, or on-demandformat where the content duration is known and finite), digital rightsmanagement (DRM) information used for playback, indications formultilingual content (e.g., audio and data fragments associated withspecific languages), and the like.

In step 408, the manifest can be transmitted, for example, to arecipient device (e.g., user device 102 (FIG. 1)) such as a source ofthe request for the manifest. The manifest may facilitate access atleast a portion of a content asset. In an aspect, a user device and/or amedia player can receive the manifest and can request particular datasegments to be received based at least on the received manifest. As anexample, a first one of the manifests can relate to a first contentsegment of a content asset. When the media player reaches the end of thefirst one of the manifests, the media player can request and receive asecond one of the manifests to continue the seamless playback of contentsuch as the next segment of the content asset or an advertisement, etc.

In step 410, the state file can be transmitted to the recipient device.The state file can facilitate the execution of one or more playbackfeatures by the recipient device. The one or more playback featuresrelate to at least the first segment of the content asset. For example,the one or more playback features can comprise one or more of anadvertising cue, content manipulation, and entitlement logic that can becaused to execute via a recipient device that does not have suchplayback features natively available.

FIG. 5 illustrates an example method for managing playback of content.In step 502, a content asset can be received or accessed. In an aspect,the content asset can be received from a content source over a network.The content asset can be received by a device configured toencode/transcode the content asset to generate one or more contentsegments for subsequent retrieval.

In step 504, a manifest can be generated. In an aspect, the manifest canbe generated based on an encoding/transcoding of the content asset.However, manifests can be generated in response to encoding/transcodingof content and can be stored for subsequent retrieval. The manifest cancomprise information associated with a location of one or more segmentsof a content asset.

In step 506, a state file can be generated. The state file can relate tothe content segments and/or the manifest. For example, the state filecan comprise information such as a time code associated with thetranscoding time of the content segments and/or the generation of theassociated manifest. The state file can comprise an event markerassociated with the content segments and/or the manifest. As an example,the event marker can represent a version of the manifest.

As an example, the state file can comprise information associated withaccess restrictions associated with the data fragments. For example,state file can comprise instructions that specific data segments are notto be skipped in playback of the content. In another aspect, the statefile can comprise indications of media format (e.g., MIME types such asvideo/mp4), type of delivery (e.g., live streaming format with accesspatterns that accommodate potentially infinite duration, or on-demandformat where the content duration is known and finite), digital rightsmanagement (DRM) information used for playback, indications formultilingual content (e.g., audio and data fragments associated withspecific languages), and the like.

In step 508, the manifest can be transmitted, for example, to arecipient device such as a source of the request for the manifest. Themanifest may facilitate access at least a portion of a content asset. Inan aspect, a user device and/or a media player can receive the manifestand can request particular data segments to be received based at leaston the received manifest. As an example, a first one of the manifestscan relate to a first content segment of a content asset. When the mediaplayer reaches the end of the first one of the manifests, the mediaplayer can request and receive a second one of the manifests to continuethe seamless playback of content such as the next segment of the contentasset or an advertisement, etc.

In step 510, the state file can be transmitted to the recipient device.The state file can facilitate the execution of one or more playbackfeatures by the recipient device. The one or more playback featuresrelate to at least the first segment of the content asset. For example,the one or more playback features can comprise one or more of anadvertising cue, content manipulation, and entitlement logic that can becaused to execute via a recipient device that does not have suchplayback features natively available.

FIG. 6 illustrates an example method for managing playback of content.In step 602, a request for a manifest can be transmitted by a device(e.g., the user device 102, the media player 112). As an example, a userdevice and/or a media player executing on the user device can comprise aweb browser (e.g., HLS enabled web browser). The user device can displaya list of available content. For example, a user can use the mediaplayer to navigate to a website presenting a list of available content.After the user selects the content for playback, a request for themanifest, such as a HTTP GET or POST request, can be sent over a networkto the computing device. For example, the user device can receive aselection of an available content and can transmit a request for themanifest.

In step 604, the manifest can be accessed or received. The manifest cancomprise information associated with a location of one or more segmentsof a content asset such as an IP address, identifier of one or morecontent assets (e.g., advertisements, video on demand assets, recordedasset) browser or operating platform, device identifiers, browsercookies or login details, screen resolution of display, and otherdevice, display, content, or user parameters. In an aspect, the manifestcan be generated in response to the request for the manifest. However,manifests can be generated in response to encoding/transcoding ofcontent and can be stored for subsequent retrieval. The manifest can beused to request at least one segment of a content asset, in step 610,and the at least one segment can be received in step 612.

In step 606, a state file can be received or accessed. The state filecan relate to the content segments and/or the manifest. For example, thestate file can comprise information such as a time code associated withthe transcoding time of the content segments and/or the generation ofthe associated manifest. The state file can comprise an event markerassociated with the content segments and/or the manifest. As an example,the event marker can represent a version of the manifest.

As an example, the state file can comprise information associated withaccess restrictions associated with the data fragments. For example,state file can comprise instructions that specific data segments are notto be skipped in playback of the content. In another aspect, the statefile can comprise indications of media format (e.g., MIME types such asvideo/mp4), type of delivery (e.g., live streaming format with accesspatterns that accommodate potentially infinite duration, or on-demandformat where the content duration is known and finite), digital rightsmanagement (DRM) information used for playback, indications formultilingual content (e.g., audio and data fragments associated withspecific languages), and the like.

In step 608, the state file can be processed to determine the identifierof the first manifest. As an example, the computing device 104 and/orthe media player 112 can process the state file to determine whichversion of the manifest is being used to retrieve content (see step610). As such, computing device 104 and/or the media player 112,plugins, and/or software applications interfacing with the media player112 can know what content is being processed by the media player 112based on the version of the manifest parsed from the state file. Sincethe version of the manifest is known and the content is known, variousplayback features can be executed that relate to the specific content inplayback, in step 614. Accordingly, the media player that may not beable to parse certain embedded information from a content stream, mayinstead process the distinct state file to facilitate playback featuresthat were previously unavailable.

FIG. 7 depicts a general-purpose computer system that includes or isconfigured to access one or more computer-accessible media. In theillustrated embodiment, a computing device 700 may include one or moreprocessors 710 a, 710 b, and/or 710 n (which may be referred hereinsingularly as the processor 710 or in the plural as the processors 710)coupled to a system memory 720 via an input/output (I/O) interface 730.The computing device 700 may further include a network interface 740coupled to an I/O interface 730.

In various embodiments, the computing device 700 may be a uniprocessorsystem including one processor 710 or a multiprocessor system includingseveral processors 710 (e.g., two, four, eight, or another suitablenumber). The processors 710 may be any suitable processors capable ofexecuting instructions. For example, in various embodiments, theprocessor(s) 710 may be general-purpose or embedded processorsimplementing any of a variety of instruction set architectures (ISAs),such as the x86, PowerPC, SPARC, or MIPS ISAs, or any other suitableISA. In multiprocessor systems, each of the processors 710 may commonly,but not necessarily, implement the same ISA.

In some embodiments, a graphics processing unit (“GPU”) 712 mayparticipate in providing graphics rendering and/or physics processingcapabilities. A GPU may, for example, comprise a highly parallelizedprocessor architecture specialized for graphical computations. In someembodiments, the processors 710 and the GPU 712 may be implemented asone or more of the same type of device.

The system memory 720 may be configured to store instructions and dataaccessible by the processor(s) 710. In various embodiments, the systemmemory 720 may be implemented using any suitable memory technology, suchas static random access memory (“SRAM”), synchronous dynamic RAM(“SDRAM”), nonvolatile/Flash®-type memory, or any other type of memory.In the illustrated embodiment, program instructions and dataimplementing one or more desired functions, such as those methods,techniques and data described above, are shown stored within the systemmemory 720 as code 725 and data 726.

In one embodiment, the I/O interface 730 may be configured to coordinateI/O traffic between the processor(s) 710, the system memory 720 and anyperipherals in the device, including an network interface 740 or otherperipheral interfaces. In some embodiments, the I/O interface 730 mayperform any necessary protocol, timing or other data transformations toconvert data signals from one component (e.g., the system memory 720)into a format suitable for use by another component (e.g., the processor710). In some embodiments, the I/O interface 730 may include support fordevices attached through various types of peripheral buses, such as avariant of the Peripheral Component Interconnect (PCI) bus standard orthe Universal Serial Bus (USB) standard, for example. In someembodiments, the function of the I/O interface 730 may be split into twoor more separate components, such as a north bridge and a south bridge,for example. Also, in some embodiments some or all of the functionalityof the I/O interface 730, such as an interface to the system memory 720,may be incorporated directly into the processor 710.

The network interface 740 may be configured to allow data to beexchanged between the computing device 700 and other device or devices760 attached to a network or networks 750, such as other computersystems or devices, for example. In various embodiments, the networkinterface 740 may support communication via any suitable wired orwireless general data networks, such as types of Ethernet networks, forexample. Additionally, the network interface 740 may supportcommunication via telecommunications/telephony networks, such as analogvoice networks or digital fiber communications networks, via storagearea networks, such as Fibre Channel SANs (storage area networks), orvia any other suitable type of network and/or protocol.

In some embodiments, the system memory 720 may be one embodiment of acomputer-accessible medium configured to store program instructions anddata as described above for implementing embodiments of thecorresponding methods and apparatus. However, in other embodiments,program instructions and/or data may be received, sent, or stored upondifferent types of computer-accessible media. Generally speaking, acomputer-accessible medium may include non-transitory storage media ormemory media, such as magnetic or optical media, e.g., disk or DVD/CDcoupled to computing device the 700 via the I/O interface 730. Anon-transitory computer-accessible storage medium may also include anyvolatile or non-volatile media, such as RAM (e.g., SDRAM, DDR SDRAM,RDRAM, SRAM, etc.), ROM, etc., that may be included in some embodimentsof the computing device 700 as the system memory 720 or another type ofmemory. Further, a computer-accessible medium may include transmissionmedia or signals, such as electrical, electromagnetic or digitalsignals, conveyed via a communication medium, such as a network and/or awireless link, such as those that may be implemented via the networkinterface 740. Portions or all of multiple computing devices, such asthose illustrated in FIG. 7, may be used to implement the describedfunctionality in various embodiments; for example, software componentsrunning on a variety of different devices and servers may collaborate toprovide the functionality. In some embodiments, portions of thedescribed functionality may be implemented using storage devices,network devices or special-purpose computer systems, in addition to orinstead of being implemented using general-purpose computer systems. Theterm “computing device,” as used herein, refers to at least all thesetypes of devices and is not limited to these types of devices.

It should also be appreciated that the systems in the figures are merelyillustrative and that other implementations might be used. Additionally,it should be appreciated that the functionality disclosed herein mightbe implemented in software, hardware, or a combination of software andhardware. Other implementations should be apparent to those skilled inthe art. It should also be appreciated that a server, gateway, or othercomputing node may include any combination of hardware or software thatmay interact and perform the described types of functionality, includingwithout limitation desktop or other computers, database servers, networkstorage devices and other network devices, PDAs, tablets, cellphones,wireless phones, pagers, electronic organizers, Internet appliances,television-based systems (e.g., using set top boxes and/orpersonal/digital video recorders), and various other consumer productsthat include appropriate communication capabilities. In addition, thefunctionality provided by the illustrated modules may in some aspects becombined in fewer modules or distributed in additional modules.Similarly, in some aspects the functionality of some of the illustratedmodules may not be provided and/or other additional functionality may beavailable.

Each of the operations, processes, methods, and algorithms described inthe preceding sections may be embodied in, and fully or partiallyautomated by, code modules executed by at least one computer or computerprocessors. The code modules may be stored on any type of non-transitorycomputer-readable medium or computer storage device, such as harddrives, solid state memory, optical disc, and/or the like. The processesand algorithms may be implemented partially or wholly inapplication-specific circuitry. The results of the disclosed processesand process steps may be stored, persistently or otherwise, in any typeof non-transitory computer storage such as, e.g., volatile ornon-volatile storage.

The various features and processes described above may be usedindependently of one another, or may be combined in various ways. Allpossible combinations and sub-combinations are intended to fall withinthe scope of this disclosure. In addition, certain method or processblocks may be omitted in some implementations. The methods and processesdescribed herein are also not limited to any particular sequence, andthe blocks or states relating thereto may be performed in othersequences that are appropriate. For example, described blocks or statesmay be performed in an order other than that specifically disclosed, ormultiple blocks or states may be combined in a single block or state.The example blocks or states may be performed in serial, in parallel, orin some other manner. Blocks or states may be added to or removed fromthe disclosed example aspects. The example systems and componentsdescribed herein may be configured differently than described. Forexample, elements may be added to, removed from, or rearranged comparedto the disclosed example aspects.

It will also be appreciated that various items are illustrated as beingstored in memory or on storage while being used, and that these items orportions of thereof may be transferred between memory and other storagedevices for purposes of memory management and data integrity.Alternatively, in other aspects some or all of the software modulesand/or systems may execute in memory on another device and communicatewith the illustrated computing systems via inter-computer communication.Furthermore, in some aspects, some or all of the systems and/or modulesmay be implemented or provided in other ways, such as at least partiallyin firmware and/or hardware, including, but not limited to, at least oneapplication-specific integrated circuits (ASICs), standard integratedcircuits, controllers (e.g., by executing appropriate instructions, andincluding microcontrollers and/or embedded controllers),field-programmable gate arrays (FPGAs), complex programmable logicdevices (CPLDs), etc. Some or all of the modules, systems and datastructures may also be stored (e.g., as software instructions orstructured data) on a computer-readable medium, such as a hard disk, amemory, a network, or a portable media article to be read by anappropriate drive or via an appropriate connection. The systems,modules, and data structures may also be transmitted as generated datasignals (e.g., as part of a carrier wave or other analog or digitalpropagated signal) on a variety of computer-readable transmission media,including wireless-based and wired/cable-based media, and may take avariety of forms (e.g., as part of a single or multiplexed analogsignal, or as multiple discrete digital packets or frames). Suchcomputer program products may also take other forms in other aspects.Accordingly, the present disclosure may be practiced with other computersystem configurations.

Conditional language used herein, such as, among others, “may,” “could,”“might,” “may,” “e.g.,” and the like, unless specifically statedotherwise, or otherwise understood within the context as used, isgenerally intended to convey that certain aspects include, while otheraspects do not include, certain features, elements, and/or steps. Thus,such conditional language is not generally intended to imply thatfeatures, elements, and/or steps are in any way required for at leastone aspects or that at least one aspects necessarily include logic fordeciding, with or without author input or prompting, whether thesefeatures, elements, and/or steps are included or are to be performed inany particular aspect. The terms “comprising,” “including,” “having,”and the like are synonymous and are used inclusively, in an open-endedfashion, and do not exclude additional elements, features, acts,operations, and so forth. Also, the term “or” is used in its inclusivesense (and not in its exclusive sense) so that when used, for example,to connect a list of elements, the term “or” means one, some, or all ofthe elements in the list.

While certain example aspects have been described, these aspects havebeen presented by way of example only, and are not intended to limit thescope of aspects disclosed herein. Thus, nothing in the foregoingdescription is intended to imply that any particular feature,characteristic, step, module, or block is necessary or indispensable.Indeed, the novel methods and systems described herein may be embodiedin a variety of other forms; furthermore, various omissions,substitutions, and changes in the form of the methods and systemsdescribed herein may be made without departing from the spirit ofaspects disclosed herein. The accompanying claims and their equivalentsare intended to cover such forms or modifications as would fall withinthe scope and spirit of certain aspects disclosed herein.

The preceding detailed description is merely exemplary in nature and isnot intended to limit the disclosure or the application and uses of thedisclosure. The described aspects are not limited to use in conjunctionwith a particular type of machine. Hence, although the presentdisclosure, for convenience of explanation, depicts and describesparticular machine, it will be appreciated that the assembly andelectronic system in accordance with this disclosure may be implementedin various other configurations and may be used in other types ofmachines. Furthermore, there is no intention to be bound by any theorypresented in the preceding background or detailed description. It isalso understood that the illustrations may include exaggerateddimensions to better illustrate the referenced items shown, and are notconsider limiting unless expressly stated as such.

It will be appreciated that the foregoing description provides examplesof the disclosed system and technique. However, it is contemplated thatother implementations of the disclosure may differ in detail from theforegoing examples. All references to the disclosure or examples thereofare intended to reference the particular example being discussed at thatpoint and are not intended to imply any limitation as to the scope ofthe disclosure more generally. All language of distinction anddisparagement with respect to certain features is intended to indicate alack of preference for those features, but not to exclude such from thescope of the disclosure entirely unless otherwise indicated.

The disclosure may include communication channels that may be any typeof wired or wireless electronic communications network, such as, e.g., awired/wireless local area network (LAN), a wired/wireless personal areanetwork (PAN), a wired/wireless home area network (HAN), awired/wireless wide area network (WAN), a campus network, a metropolitannetwork, an enterprise private network, a virtual private network (VPN),an internetwork, a backbone network (BBN), a global area network (GAN),the Internet, an intranet, an extranet, an overlay network, a cellulartelephone network, a Personal Communications Service (PCS), using knownprotocols such as the Global System for Mobile Communications (GSM),CDMA (Code-Division Multiple Access), Long Term Evolution (LTE), W-CDMA(Wideband Code-Division Multiple Access), Wireless Fidelity (Wi-Fi),Bluetooth, and/or the like, and/or a combination of two or more thereof

Additionally, the various aspects of the disclosure may be implementedin a non-generic computer implementation. Moreover, the various aspectsof the disclosure set forth herein improve the functioning of the systemas is apparent from the disclosure hereof. Furthermore, the variousaspects of the disclosure involve computer hardware that it specificallyprogrammed to solve the complex problem addressed by the disclosure.Accordingly, the various aspects of the disclosure improve thefunctioning of the system overall in its specific implementation toperform the process set forth by the disclosure and as defined by theclaims.

Recitation of ranges of values herein are merely intended to serve as ashorthand method of referring individually to each separate valuefalling within the range, unless otherwise indicated herein, and eachseparate value is incorporated into the specification as if it wereindividually recited herein. All methods described herein may beperformed in any suitable order unless otherwise indicated herein orotherwise clearly contradicted by context.

The methods and systems can employ artificial intelligence techniquessuch as machine learning and iterative learning. Examples of suchtechniques include, but are not limited to, expert systems, case basedreasoning, Bayesian networks, behavior based AI, neural networks, fuzzysystems, evolutionary computation (e.g. genetic algorithms), swarmintelligence (e.g. ant algorithms), and hybrid intelligent systems (e.g.expert inference rules generated through a neural network or productionrules from statistical learning).

While the methods and systems have been described in connection withpreferred embodiments and specific examples, it is not intended that thescope be limited to the particular embodiments set forth, as theembodiments herein are intended in all respects to be illustrativerather than restrictive.

Unless otherwise expressly stated, it is in no way intended that anymethod set forth herein be construed as requiring that its steps beperformed in a specific order. Accordingly, where a method claim doesnot actually recite an order to be followed by its steps or it is nototherwise specifically stated in the claims or descriptions that thesteps are to be limited to a specific order, it is no way intended thatan order be inferred, in any respect. This holds for any possiblenon-express basis for interpretation, including: matters of logic withrespect to arrangement of steps or operational flow; plain meaningderived from grammatical organization or punctuation; the number or typeof embodiments described in the specification.

It is to be understood that the terminology used herein is for thepurpose of describing particular embodiments only and is not intended tobe limiting.

As used in the specification and the appended claims, the singular forms“a,” “an,” and “the” include plural referents unless the context clearlydictates otherwise. Ranges may be expressed herein as from “about” oneparticular value, and/or to “about” another particular value. When sucha range is expressed, another embodiment includes from the oneparticular value and/or to the other particular value. Similarly, whenvalues are expressed as approximations, by use of the antecedent“about,” it will be understood that the particular value forms anotherembodiment. It will be further understood that the endpoints of each ofthe ranges are significant both in relation to the other endpoint, andindependently of the other endpoint.

“Optional” or “optionally” means that the subsequently described eventor circumstance may or may not occur, and that the description includesinstances where said event or circumstance occurs and instances where itdoes not.

Throughout the description and claims of this specification, the word“comprise” and variations of the word, such as “comprising” and“comprises,” means “including but not limited to,” and is not intendedto exclude, for example, other components, integers or steps.“Exemplary” means “an example of” and is not intended to convey anindication of a preferred or ideal embodiment. “Such as” is not used ina restrictive sense, but for explanatory purposes.

Disclosed are components that can be used to perform the disclosedmethods and comprise the disclosed systems. These and other componentsare disclosed herein, and it is understood that when combinations,subsets, interactions, groups, etc. of these components are disclosedthat while specific reference of each various individual and collectivecombination and permutation of these may not be explicitly disclosed,each is specifically contemplated and described herein, for all methodsand systems. This applies to all aspects of this application including,but not limited to, steps in disclosed methods. Thus, if there are avariety of additional steps that can be performed it is understood thateach of these additional steps can be performed with any specificembodiment or combination of embodiments of the disclosed methods.

The present methods and systems may be understood more readily byreference to the following detailed description of preferred embodimentsand the examples included therein and to the Figures and their previousand following description.

As will be appreciated by one skilled in the art, the methods andsystems may take the form of an entirely hardware embodiment, anentirely software embodiment, or an embodiment combining software andhardware aspects. Furthermore, the methods and systems may take the formof a computer program product on a computer-readable storage mediumhaving computer-readable program instructions (e.g., computer software)embodied in the storage medium. More particularly, the present methodsand systems may take the form of web-implemented computer software. Anysuitable computer-readable storage medium may be utilized including harddisks, CD-ROMs, optical storage devices, or magnetic storage devices.

Embodiments of the methods and systems are described below withreference to block diagrams and flowchart illustrations of methods,systems, apparatuses and computer program products. It will beunderstood that each block of the block diagrams and flowchartillustrations, and combinations of blocks in the block diagrams andflowchart illustrations, respectively, can be implemented by computerprogram instructions. These computer program instructions may be loadedonto a general purpose computer, special purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions which execute on the computer or other programmabledata processing apparatus create a means for implementing the functionsspecified in the flowchart block or blocks.

These computer program instructions may also be stored in acomputer-readable memory that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including computer-readableinstructions for implementing the function specified in the flowchartblock or blocks. The computer program instructions may also be loadedonto a computer or other programmable data processing apparatus to causea series of operational steps to be performed on the computer or otherprogrammable apparatus to produce a computer-implemented process suchthat the instructions that execute on the computer or other programmableapparatus provide steps for implementing the functions specified in theflowchart block or blocks.

Accordingly, blocks of the block diagrams and flowchart illustrationssupport combinations of means for performing the specified functions,combinations of steps for performing the specified functions and programinstruction means for performing the specified functions. It will alsobe understood that each block of the block diagrams and flowchartillustrations, and combinations of blocks in the block diagrams andflowchart illustrations, can be implemented by special purposehardware-based computer systems that perform the specified functions orsteps, or combinations of special purpose hardware and computerinstructions.

It will be apparent to those skilled in the art that variousmodifications and variations can be made without departing from thescope or spirit. Other embodiments will be apparent to those skilled inthe art from consideration of the specification and practice disclosedherein. It is intended that the specification and examples be consideredas exemplary only, with a true scope and spirit being indicated by thefollowing claims.

What is claimed:
 1. A method comprising: determining, by a computingdevice, a manifest associated with a content asset, wherein the manifestcomprises an indication of one or more content segments of the contentasset and a storage location of the one or more content segments;determining a state file comprising an identifier associated with themanifest and one or more playback features; sending, to a recipientdevice, the manifest; and sending, to the recipient device, the statefile to facilitate modifying, based on the playback features and theidentifier, playback of at least a portion of the one or more contentsegments.
 2. The method of claim 1, wherein the identifier associatedwith the manifest comprises an identifier indicating the manifest fromamong a plurality of manifests associated with the content asset.
 3. Themethod of claim 1, wherein the identifier associated with the manifestis associated with a bit rate of the one or more content segments, alanguage of the one or more content segments, an image size of the oneor more content segments, a limitation of the one or more contentsegments, or a combination thereof
 4. The method of claim 1, wherein theone or more playback features comprise one or more of an advertisingcue, language information, content format, content manipulation, orentitlement information.
 5. The method of claim 1, wherein sending thestate file comprises sending, to a media player of the recipient device,the state file, wherein the media player is not configured to decode,from the content asset, data indicating the one or more playbackfeatures.
 6. The method of claim 1, wherein determining the state filecomprises generating the state file as part of a transcoding processassociated with the content asset.
 7. The method of claim 1, wherein thestate file is time synchronized, based on one or more time codes in thestate file, with the manifest.
 8. A method comprising: receiving, amanifest associated with a request for content, wherein the manifestcomprises an indication of at least one content segment and a storagelocation of the at least one content segment; receiving a state filethat comprises data associated with one or more playback features;determining, based on the state file, an identifier associated with oneor more of the manifest or the at least one content segment;determining, based on the identifier, that the one or more playbackfeatures are associated with one or more of the manifest or the at leastone content segment; and outputting, in accordance with the one or moreplayback features, the content.
 9. The method of claim 8, wherein theidentifier comprises an identifier indicating the manifest from among aplurality of manifests associated with the content.
 10. The method ofclaim 8, wherein the identifier is associated with a bit rate of the atleast one content segment, a language of the at least one contentsegment, an image size of the at least one content segment, a limitationof the at least one content segment, or a combination thereof
 11. Themethod of claim 8, wherein the one or more playback features compriseone or more of an advertising cue, language information, content format,content manipulation, or entitlement information.
 12. The method ofclaim 8, wherein receiving the state file comprises receiving the statefile by a media player that is not configured to decode, from thecontent, data indicating the one or more playback features.
 13. Themethod of claim 8, wherein state file is generated, by a transcoder, aspart of a transcoding process associated with the content.
 14. Themethod of claim 8, wherein the state file is time synchronized, based onone or more time codes in the state file, with the manifest.
 15. Adevice comprising: one or more processors; and memory storinginstructions that, when executed by the one or more processors, causethe device to: receive, a manifest associated with a request forcontent, wherein the manifest comprises an indication of at least onecontent segment and a storage location of the at least one contentsegment; receive a state file that comprises data associated with one ormore playback features; determine, based on the state file, anidentifier associated with one or more of the manifest or the at leastone content segment; determine, based on the identifier, that the one ormore playback features are associated with one or more of the manifestor the at least one content segment; and output, in accordance with theone or more playback features, the content.
 16. The device of claim 15,wherein the identifier comprises an identifier indicating the manifestfrom among a plurality of manifests associated with the content.
 17. Thedevice of claim 15, wherein the identifier is associated with a bit rateof the at least one content segment, a language of the at least onecontent segment, an image size of the at least one content segment, alimitation of the at least one content segment, or a combinationthereof.
 18. The device of claim 15, wherein the one or more playbackfeatures comprise one or more of an advertising cue, languageinformation, content format, content manipulation, or entitlementinformation.
 19. The device of claim 15, wherein the instructions that,when executed, cause the device to receive the state file comprisesinstructions that, when executed, cause the device to receive the statefile by a media player that is not configured to decode, from thecontent, data indicating the one or more playback features.
 20. Thedevice of claim 15, wherein state file is generated, by a transcoder, aspart of a transcoding process associated with the content.